Storage Encryption

ABSTRACT

Storage associated with a virtual machine or other type of device may be migrated between locations (e.g., physical devices, network locations, etc.). To maintain the security of the storage, a system may manage the encryption of the storage area such that a storage area is encrypted with a first encryption key that may be maintained through the migration. A header of the storage area, on the other hand, may be encrypted using a second encryption key and the first encryption key may be stored therein. Upon transfer, the header may be re-encrypted to affect the transfer of security.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/748,032, filed on Jan. 23, 2013, which claims the benefit of priorityfrom and is a non-provisional application of U.S. ProvisionalApplication Ser. No. 61/589,591, entitled “STORAGE ENCRYPTION” and filedJan. 23, 2012. The contents of the aforementioned applications arehereby incorporated by reference in their entirety.

BACKGROUND

Virtual machines may be migrated between different devices and/or hosts.Virtual machines may further be associated with storage repositoriesthat are provisioned for use by those virtual machines. For security,the storage repositories may be encrypted using various encryptionalgorithms and protocols.

In some arrangements, a user or service provider or other entity maywish to migrate a virtual machine from one device to another. In suchinstances, the original device may still have access to the storagerepository, for example, if the original host knows of the appropriateencryption keys or decryption codes. Accordingly, a system and method isneeded to migrate virtual machines between devices while maintainingeffective security controls and management of their associated storagerepositories.

SUMMARY

In light of the foregoing background, the following presents asimplified summary of the present disclosure in order to provide a basicunderstanding of some aspects described herein. This summary is not anextensive overview, and is not intended to identify key or criticalelements or to delineate the scope of the claims. The following summarymerely presents various described aspects in a simplified form as aprelude to the more detailed description provided below.

In order to address the above shortcomings and additional benefits thatwill be realized upon reading the disclosure, aspects herein provide asystem and method for maintaining storage repository security whentransferring the repository from one device another. In one example, thedata storage system of the storage repository may be encrypted using afirst key, K1, and K1 may be stored in a header of the storagerepository. To control access to the data storage system, the storagerepository key K1 may be encrypted using a second key, K2. Accordingly,access to the encrypted file system may thus be controlled by theencryption of the key K1, without having to replace, decrypt andre-encrypt the entire file system. When the virtual machine is to bemigrated, a device may initially generate a transfer key and encrypt thestorage key K1 with the transfer key. The virtual machine is thenmigrated to the new device along with the transfer key and the storageheader section. The new device may then generate a new encryption key K3(not known to the original device) for encrypting the storage repositorykey K1.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described aspects of the disclosure in general terms,reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1A depicts embodiments of network environments that provide remoteaccess to computing devices that can execute application programs.

FIG. 1B and FIG. 1C are block diagrams that depict embodiments ofcomputing devices.

FIG. 2A and FIG. 2B are block diagrams that depict embodiments of avirtualization environment.

FIG. 3 is a block diagram that depicts embodiments of a virtualizationenvironment and a virtual desktop infrastructure environment.

FIG. 4 is a flowchart illustrating an example process by which a virtualmachine may be migrated from one device to another according to one ormore aspects described herein.

FIG. 5 illustrates an example block diagram illustrating a data storagerepository structure according to one or more aspects described herein.

FIGS. 6A-6D illustrate a virtual machine migration process according toone or more aspects described herein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings, which form a part hereof, and inwhich is shown by way of illustration various embodiments in whichaspects described herein may be practiced. It is to be understood thatother embodiments may be utilized and structural and functionalmodifications may be made without departing from the scope and spirit ofthe present disclosure.

As will be appreciated by one of skill in the art upon reading thefollowing disclosure, various aspects described herein may be embodiedas a method, a data processing system, or a computer program product.Accordingly, those aspects may take the form of an entirely hardwareembodiment, an entirely software embodiment or an embodiment combiningsoftware and hardware aspects. Furthermore, such aspects may take theform of a computer program product stored by one or morecomputer-readable storage media having computer-readable program code,or instructions, embodied in or on the storage media. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various signals representing data orevents as described herein may be transferred between a source and adestination in the form of electromagnetic waves traveling throughsignal-conducting media such as metal wires, optical fibers, and/orwireless transmission media (e.g., air and/or space).

FIG. 1A illustrates one embodiment of a computing environment 101 thatincludes one or more client machines 102A-102N (generally referred toherein as “client machine(s) 102”) in communication with one or moreservers 106A-106N (generally referred to herein as “server(s) 106”).Installed in between the client machine(s) 102 and server(s) 106 is anetwork.

In one embodiment, the computing environment 101 can include anappliance installed between the server(s) 106 and client machine(s) 102.This appliance can manage client/server connections, and in some casescan load balance client connections amongst a plurality of backendservers.

The client machine(s) 102 can in some embodiment be referred to as asingle client machine 102 or a single group of client machines 102,while server(s) 106 may be referred to as a single server 106 or asingle group of servers 106. In one embodiment a single client machine102 communicates with more than one server 106, while in anotherembodiment a single server 106 communicates with more than one clientmachine 102. In yet another embodiment, a single client machine 102communicates with a single server 106.

A client machine 102 can, in some embodiments, be referenced by any oneof the following terms: client machine(s) 102; client(s); clientcomputer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); endpoint node(s);or a second machine. The server 106, in some embodiments, may bereferenced by any one of the following terms: server(s), local machine;remote machine; server farm(s), host computing device(s), or a firstmachine(s).

In one embodiment, the client machine 102 can be a virtual machine 102C.The virtual machine 102C can be any virtual machine, while in someembodiments the virtual machine 102C can be any virtual machine managedby a hypervisor developed by XenSolutions, Citrix Systems, IBM, VMware,or any other hypervisor. In other embodiments, the virtual machine 102Ccan be managed by any hypervisor, while in still other embodiments, thevirtual machine 102C can be managed by a hypervisor executing on aserver 106 or a hypervisor executing on a client 102.

The client machine 102 can in some embodiments execute, operate orotherwise provide an application that can be any one of the following:software; a program; executable instructions; a virtual machine; ahypervisor; a web browser; a web-based client; a client-serverapplication; a thin-client computing client; an ActiveX control; a Javaapplet; software related to voice over internet protocol (VoIP)communications like a soft IP telephone; an application for streamingvideo and/or audio; an application for facilitating real-time-datacommunications; a HTTP client; a FTP client; an Oscar client; a Telnetclient; or any other set of executable instructions. Still otherembodiments include a client device 102 that displays application outputgenerated by an application remotely executing on a server 106 or otherremotely located machine. In these embodiments, the client device 102can display the application output in an application window, a browser,or other output window. In one embodiment, the application is a desktop,while in other embodiments the application is an application thatgenerates a desktop.

The server 106, in some embodiments, executes a remote presentationclient or other client or program that uses a thin-client orremote-display protocol to capture display output generated by anapplication executing on a server 106 and transmits the applicationdisplay output to a remote client 102. The thin-client or remote-displayprotocol can be any one of the following protocols: the IndependentComputing Architecture (ICA) protocol manufactured by Citrix Systems,Inc. of Ft. Lauderdale, Fla.; or the Remote Desktop Protocol (RDP)manufactured by the Microsoft Corporation of Redmond, Wash.

The computing environment 101 can include more than one server 106A-106Nsuch that the servers 106A-106N are logically grouped together into aserver farm 106. The server farm 106 can include servers 106 that aregeographically dispersed and logically grouped together in a server farm106, or servers 106 that are located proximate to each other andlogically grouped together in a server farm 106. Geographicallydispersed servers 106A-106N within a server farm 106 can, in someembodiments, communicate using a WAN, MAN, or LAN, where differentgeographic regions can be characterized as: different continents;different regions of a continent; different countries; different states;different cities; different campuses; different rooms; or anycombination of the preceding geographical locations. In some embodimentsthe server farm 106 may be administered as a single entity, while inother embodiments the server farm 106 can include multiple server farms106.

In some embodiments, a server farm 106 can include servers 106 thatexecute a substantially similar type of operating system platform (e.g.,WINDOWS NT, manufactured by Microsoft Corp. of Redmond, Wash., UNIX,LINUX, or SNOW LEOPARD.) In other embodiments, the server farm 106 caninclude a first group of servers 106 that execute a first type ofoperating system platform, and a second group of servers 106 thatexecute a second type of operating system platform. The server farm 106,in other embodiments, can include servers 106 that execute differenttypes of operating system platforms.

The server 106, in some embodiments, can be any server type. In otherembodiments, the server 106 can be any of the following server types: afile server; an application server; a web server; a proxy server; anappliance; a network appliance; a gateway; an application gateway; agateway server; a virtualization server; a deployment server; a SSL VPNserver; a firewall; a web server; an application server or as a masterapplication server; a server 106 executing an active directory; or aserver 106 executing an application acceleration program that providesfirewall functionality, application functionality, or load balancingfunctionality. In some embodiments, a server 106 may be a RADIUS serverthat includes a remote authentication dial-in user service. Inembodiments where the server 106 comprises an appliance, the server 106can be an appliance manufactured by any one of the followingmanufacturers: the Citrix Application Networking Group; Silver PeakSystems, Inc; Riverbed Technology, Inc.; F5 Networks, Inc.; or JuniperNetworks, Inc. Some embodiments include a first server 106A thatreceives requests from a client machine 102, forwards the request to asecond server 106B, and responds to the request generated by the clientmachine 102 with a response from the second server 106B. The firstserver 106A can acquire an enumeration of applications available to theclient machine 102 and well as address information associated with anapplication server 106 hosting an application identified within theenumeration of applications. The first server 106A can then present aresponse to the client's request using a web interface, and communicatedirectly with the client 102 to provide the client 102 with access to anidentified application.

The server 106 can, in some embodiments, execute any one of thefollowing applications: a thin-client application using a thin-clientprotocol to transmit application display data to a client; a remotedisplay presentation application; any portion of the CITRIX ACCESS SUITEby Citrix Systems, Inc. like the METAFRAME or CITRIX PRESENTATIONSERVER; MICROSOFT WINDOWS Terminal Services manufactured by theMicrosoft Corporation; or an ICA client, developed by Citrix Systems,Inc. Another embodiment includes a server 106 that is an applicationserver such as: an email server that provides email services such asMICROSOFT EXCHANGE manufactured by the Microsoft Corporation; a web orInternet server; a desktop sharing server; a collaboration server; orany other type of application server. Still other embodiments include aserver 106 that executes any one of the following types of hostedservers applications: GOTOMEETING provided by Citrix Online Division,Inc.; WEBEX provided by WebEx, Inc. of Santa Clara, Calif.; or MicrosoftOffice LIVE MEETING provided by Microsoft Corporation.

Client machines 102 can, in some embodiments, be a client node thatseeks access to resources provided by a server 106. In otherembodiments, the server 106 may provide clients 102 or client nodes withaccess to hosted resources. The server 106, in some embodiments,functions as a master node such that it communicates with one or moreclients 102 or servers 106. In some embodiments, the master node canidentify and provide address information associated with a server 106hosting a requested application, to one or more clients 102 or servers106. In still other embodiments, the master node can be a server farm106, a client 102, a cluster of client nodes 102, or an appliance.

One or more clients 102 and/or one or more servers 106 can transmit dataover a network 104 installed between machines and appliances within thecomputing environment 101. The network 104 can comprise one or moresub-networks, and can be installed between any combination of theclients 102, servers 106, computing machines and appliances includedwithin the computing environment 101. In some embodiments, the network104 can be: a local-area network (LAN); a metropolitan area network(MAN); a wide area network (WAN); a primary network 104 comprised ofmultiple sub-networks 104 located between the client machines 102 andthe servers 106; a primary public network 104 with a private sub-network104; a primary private network 104 with a public sub-network 104; or aprimary private network 104 with a private sub-network 104. Stillfurther embodiments include a network 104 that can be any of thefollowing network types: a point to point network; a broadcast network;a telecommunications network; a data communication network; a computernetwork; an ATM (Asynchronous Transfer Mode) network; a SONET(Synchronous Optical Network) network; a SDH (Synchronous DigitalHierarchy) network; a wireless network; a wireline network; or a network104 that includes a wireless link where the wireless link can be aninfrared channel or satellite band. The network topology of the network104 can differ within different embodiments, possible network topologiesinclude: a bus network topology; a star network topology; a ring networktopology; a repeater-based network topology; or a tiered-star networktopology. Additional embodiments may include a network 104 of mobiletelephone networks that use a protocol to communicate among mobiledevices, where the protocol can be any one of the following: AMPS; TDMA;CDMA; GSM; GPRS UMTS; or any other protocol able to transmit data amongmobile devices.

Illustrated in FIG. 1B is an embodiment of a computing device 100, wherethe client machine 102 and server 106 illustrated in FIG. 1A can bedeployed as and/or executed on any embodiment of the computing device100 illustrated and described herein. Included within the computingdevice 100 is a system bus 150 that communicates with the followingcomponents: a central processing unit 121; a main memory 122; storagememory 128; an input/output (I/O) controller 123; display devices124A-124N; an installation device 116; and a network interface 118. Inone embodiment, the storage memory 128 includes: an operating system,software routines, and a client agent 120. The I/O controller 123, insome embodiments, is further connected to a key board 126, and apointing device 127. Other embodiments may include an I/O controller 123connected to more than one input/output device 130A-130N.

FIG. 1C illustrates one embodiment of a computing device 100, where theclient machine 102 and server 106 illustrated in FIG. 1A can be deployedas and/or executed on any embodiment of the computing device 100illustrated and described herein. Included within the computing device100 is a system bus 150 that communicates with the following components:a bridge 170, and a first I/O device 130A. In another embodiment, thebridge 170 is in further communication with the main central processingunit 121, where the central processing unit 121 can further communicatewith a second I/O device 130B, a main memory 122, and a cache memory140. Included within the central processing unit 121, are I/O ports, amemory port 103, and a main processor.

Embodiments of the computing machine 100 can include a centralprocessing unit 121 characterized by any one of the following componentconfigurations: logic circuits that respond to and process instructionsfetched from the main memory unit 122; a microprocessor unit, such as:those manufactured by Intel Corporation; those manufactured by MotorolaCorporation; those manufactured by Transmeta Corporation of Santa Clara,Calif.; the RS/6000 processor such as those manufactured byInternational Business Machines; a processor such as those manufacturedby Advanced Micro Devices; or any other combination of logic circuits.Still other embodiments of the central processing unit 122 may includeany combination of the following: a microprocessor, a microcontroller, acentral processing unit with a single processing core, a centralprocessing unit with two processing cores, or a central processing unitwith more than one processing core.

While FIG. 1C illustrates a computing device 100 that includes a singlecentral processing unit 121, in some embodiments the computing device100 can include one or more processing units 121. In these embodiments,the computing device 100 may store and execute firmware or otherexecutable instructions that, when executed, direct the one or moreprocessing units 121 to simultaneously execute instructions or tosimultaneously execute instructions on a single piece of data. In otherembodiments, the computing device 100 may store and execute firmware orother executable instructions that, when executed, direct the one ormore processing units to each execute a section of a group ofinstructions. For example, each processing unit 121 may be instructed toexecute a portion of a program or a particular module within a program.

In some embodiments, the processing unit 121 can include one or moreprocessing cores. For example, the processing unit 121 may have twocores, four cores, eight cores, etc. In one embodiment, the processingunit 121 may comprise one or more parallel processing cores. Theprocessing cores of the processing unit 121, may in some embodimentsaccess available memory as a global address space, or in otherembodiments, memory within the computing device 100 can be segmented andassigned to a particular core within the processing unit 121. In oneembodiment, the one or more processing cores or processors in thecomputing device 100 can each access local memory. In still anotherembodiment, memory within the computing device 100 can be shared amongstone or more processors or processing cores, while other memory can beaccessed by particular processors or subsets of processors. Inembodiments where the computing device 100 includes more than oneprocessing unit, the multiple processing units can be included in asingle integrated circuit (IC). These multiple processors, in someembodiments, can be linked together by an internal high speed bus, whichmay be referred to as an element interconnect bus.

In embodiments where the computing device 100 includes one or moreprocessing units 121, or a processing unit 121 including one or moreprocessing cores, the processors can execute a single instructionsimultaneously on multiple pieces of data (SIMD), or in otherembodiments can execute multiple instructions simultaneously on multiplepieces of data (MIMD). In some embodiments, the computing device 100 caninclude any number of SIMD and MIMD processors.

The computing device 100, in some embodiments, can include a graphicsprocessor or a graphics processing unit (Not Shown). The graphicsprocessing unit can include any combination of software and hardware,and can further input graphics data and graphics instructions, render agraphic from the inputted data and instructions, and output the renderedgraphic. In some embodiments, the graphics processing unit can beincluded within the processing unit 121. In other embodiments, thecomputing device 100 can include one or more processing units 121, whereat least one processing unit 121 is dedicated to processing andrendering graphics.

One embodiment of the computing machine 100 includes a centralprocessing unit 121 that communicates with cache memory 140 via asecondary bus also known as a backside bus, while another embodiment ofthe computing machine 100 includes a central processing unit 121 thatcommunicates with cache memory via the system bus 150. The local systembus 150 can, in some embodiments, also be used by the central processingunit to communicate with more than one type of I/O device 130A-130N. Insome embodiments, the local system bus 150 can be any one of thefollowing types of buses: a VESA VL bus; an ISA bus; an EISA bus; aMicroChannel Architecture (MCA) bus; a PCI bus; a PCI-X bus; aPCI-Express bus; or a NuBus. Other embodiments of the computing machine100 include an I/O device 130A-130N that is a video display 124 thatcommunicates with the central processing unit 121. Still other versionsof the computing machine 100 include a processor 121 connected to an I/Odevice 130A-130N via any one of the following connections:HyperTransport, Rapid I/O, or InfiniBand. Further embodiments of thecomputing machine 100 include a processor 121 that communicates with oneI/O device 130A using a local interconnect bus and a second I/O device130B using a direct connection.

The computing device 100, in some embodiments, includes a main memoryunit 122 and cache memory 140. The cache memory 140 can be any memorytype, and in some embodiments can be any one of the following types ofmemory: SRAM; BSRAM; or EDRAM. Other embodiments include cache memory140 and a main memory unit 122 that can be any one of the followingtypes of memory: Static random access memory (SRAM), Burst SRAM orSynchBurst SRAM (BSRAM); Dynamic random access memory (DRAM); Fast PageMode DRAM (FPM DRAM); Enhanced DRAM (EDRAM), Extended Data Output RAM(EDO RAM); Extended Data Output DRAM (EDO DRAM); Burst Extended DataOutput DRAM (BEDO DRAM); Enhanced DRAM (EDRAM); synchronous DRAM(SDRAM); JEDEC SRAM; PC100 SDRAM; Double Data Rate SDRAM (DDR SDRAM);Enhanced SDRAM (ESDRAM); SyncLink DRAM (SLDRAM); Direct Rambus DRAM(DRDRAM); Ferroelectric RAM (FRAM); or any other type of memory. Furtherembodiments include a central processing unit 121 that can access themain memory 122 via: a system bus 150; a memory port 103; or any otherconnection, bus or port that allows the processor 121 to access memory122.

One embodiment of the computing device 100 provides support for any oneof the following installation devices 116: a CD-ROM drive, a CD-R/RWdrive, a DVD-ROM drive, tape drives of various formats, USB device, abootable medium, a bootable CD, a bootable CD for GNU/Linux distributionsuch as KNOPPIX®, a hard-drive or any other device suitable forinstalling applications or software. Applications can in someembodiments include a client agent 120, or any portion of a client agent120. The computing device 100 may further include a storage device 128that can be either one or more hard disk drives, or one or moreredundant arrays of independent disks; where the storage device isconfigured to store an operating system, software, programsapplications, or at least a portion of the client agent 120. A furtherembodiment of the computing device 100 includes an installation device116 that is used as the storage device 128.

The computing device 100 may further include a network interface 118 tointerface to a Local Area Network (LAN), Wide Area Network (WAN) or theInternet through a variety of connections including, but not limited to,standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T3, 56kb,X.25, SNA, DECNET), broadband connections (e.g., ISDN, Frame Relay, ATM,Gigabit Ethernet, Ethernet-over-SONET), wireless connections, or somecombination of any or all of the above. Connections can also beestablished using a variety of communication protocols (e.g., TCP/IP,IPX, SPX, NetBIOS, Ethernet, ARCNET, SONET, SDH, Fiber Distributed DataInterface (FDDI), RS232, RS485, IEEE 802.11, IEEE 802.11a, IEEE 802.11b,IEEE 802.11g, CDMA, GSM, WiMax and direct asynchronous connections). Oneversion of the computing device 100 includes a network interface 118able to communicate with additional computing devices 100′ via any typeand/or form of gateway or tunneling protocol such as Secure Socket Layer(SSL) or Transport Layer Security (TLS), or the Citrix Gateway Protocolmanufactured by Citrix Systems, Inc. Versions of the network interface118 can comprise any one of: a built-in network adapter; a networkinterface card; a PCMCIA network card; a card bus network adapter; awireless network adapter; a USB network adapter; a modem; or any otherdevice suitable for interfacing the computing device 100 to a networkcapable of communicating and performing the methods and systemsdescribed herein.

Embodiments of the computing device 100 include any one of the followingI/O devices 130A-130N: a keyboard 126; a pointing device 127; mice;trackpads; an optical pen; trackballs; microphones; drawing tablets;video displays; speakers; inkjet printers; laser printers; anddye-sublimation printers; or any other input/output device able toperform the methods and systems described herein. An I/O controller 123may in some embodiments connect to multiple I/O devices 103A-130N tocontrol the one or more I/O devices. Some embodiments of the I/O devices130A-130N may be configured to provide storage or an installation medium116, while others may provide a universal serial bus (USB) interface forreceiving USB storage devices such as the USB Flash Drive line ofdevices manufactured by Twintech Industry, Inc. Still other embodimentsinclude an I/O device 130 that may be a bridge between the system bus150 and an external communication bus, such as: a USB bus; an AppleDesktop Bus; an RS-232 serial connection; a SCSI bus; a FireWire bus; aFireWire 800 bus; an Ethernet bus; an AppleTalk bus; a Gigabit Ethernetbus; an Asynchronous Transfer Mode bus; a HIPPI bus; a Super HIPPI bus;a SerialPlus bus; a SCI/LAMP bus; a FibreChannel bus; or a SerialAttached small computer system interface bus.

In some embodiments, the computing machine 100 can connect to multipledisplay devices 124A-124N, in other embodiments the computing device 100can connect to a single display device 124, while in still otherembodiments the computing device 100 connects to display devices124A-124N that are the same type or form of display, or to displaydevices that are different types or forms. Embodiments of the displaydevices 124A-124N can be supported and enabled by the following: one ormultiple I/O devices 130A-130N; the I/O controller 123; a combination ofI/O device(s) 130A-130N and the I/O controller 123; any combination ofhardware and software able to support a display device 124A-124N; anytype and/or form of video adapter, video card, driver, and/or library tointerface, communicate, connect or otherwise use the display devices124A-124N. The computing device 100 may in some embodiments beconfigured to use one or multiple display devices 124A-124N, theseconfigurations include: having multiple connectors to interface tomultiple display devices 124A-124N; having multiple video adapters, witheach video adapter connected to one or more of the display devices124A-124N; having an operating system configured to support multipledisplays 124A-124N; using circuits and software included within thecomputing device 100 to connect to and use multiple display devices124A-124N; and executing software on the main computing device 100 andmultiple secondary computing devices to enable the main computing device100 to use a secondary computing device's display as a display device124A-124N for the main computing device 100. Still other embodiments ofthe computing device 100 may include multiple display devices 124A-124Nprovided by multiple secondary computing devices and connected to themain computing device 100 via a network.

In some embodiments, the computing machine 100 can execute any operatingsystem, while in other embodiments the computing machine 100 can executeany of the following operating systems: versions of the MICROSOFTWINDOWS operating systems such as WINDOWS 3.x; WINDOWS 95; WINDOWS 98;WINDOWS 2000; WINDOWS NT 3.51; WINDOWS NT 4.0; WINDOWS CE; WINDOWS XP;and WINDOWS VISTA; the different releases of the Unix and Linuxoperating systems; any version of the MAC OS manufactured by AppleComputer; OS/2, manufactured by International Business Machines; anyembedded operating system; any real-time operating system; any opensource operating system; any proprietary operating system; any operatingsystems for mobile computing devices; or any other operating system. Instill another embodiment, the computing machine 100 can execute multipleoperating systems. For example, the computing machine 100 can executePARALLELS or another virtualization platform that can execute or managea virtual machine executing a first operating system, while thecomputing machine 100 executes a second operating system different fromthe first operating system.

The computing machine 100 can be embodied in any one of the followingcomputing devices: a computing workstation; a desktop computer; a laptopor notebook computer; a server; a handheld computer; a mobile telephone;a portable telecommunication device; a media playing device; a gamingsystem; a mobile computing device; a netbook; a device of the IPODfamily of devices manufactured by Apple Computer; any one of thePLAYSTATION family of devices manufactured by the Sony Corporation; anyone of the Nintendo family of devices manufactured by Nintendo Co; anyone of the XBOX family of devices manufactured by the MicrosoftCorporation; or any other type and/or form of computing,telecommunications or media device that is capable of communication andthat has sufficient processor power and memory capacity to perform themethods and systems described herein. In other embodiments the computingmachine 100 can be a mobile device such as any one of the followingmobile devices: a JAVA-enabled cellular telephone or personal digitalassistant (PDA), such as the i55sr, i58sr, i85s, i88s, i90c, i95cl, orthe im1100, all of which are manufactured by Motorola Corp; the 6035 orthe 7135, manufactured by Kyocera; the i300 or i330, manufactured bySamsung Electronics Co., Ltd; the TREO 180, 270, 600, 650, 680, 700p,700w, or 750 smart phone manufactured by Palm, Inc; any computing devicethat has different processors, operating systems, and input devicesconsistent with the device; or any other mobile computing device capableof performing the methods and systems described herein. In still otherembodiments, the computing device 100 can be any one of the followingmobile computing devices: any one series of Blackberry, or otherhandheld device manufactured by Research In Motion Limited; the iPhonemanufactured by Apple Computer; Palm Pre; a Pocket PC; a Pocket PCPhone; or any other handheld mobile device.

Illustrated in FIG. 2A is one embodiment of a virtualizationenvironment. Included on a computing device 201 is a hardware layer thatcan include one or more physical disks 204, one or more physical devices206, one or more physical processors 208 and a physical memory 216. Insome embodiments, firmware 212 can be stored within a memory element inthe physical memory 216 and can be executed by one or more of thephysical processors 208. The computing device 201 can further include anoperating system 214 that can be stored in a memory element in thephysical memory 216 and executed by one or more of the physicalprocessors 208. Still further, a hypervisor 202 can be stored in amemory element in the physical memory 216 and can be executed by one ormore of the physical processors 208. Executing on one or more of thephysical processors 208 can be one or more virtual machines 232A-C(generally 232). Each virtual machine 232 can have a virtual disk 226A-Cand a virtual processor 228A-C.

As illustrated in FIG. 2A, virtual disks are not limited to storagedevices located in the same physical device as the devices on which thevirtual machines are instantiated. Instead, the virtual disks such asvirtual disk 226A and 226B may be provided or provisioned on a networkstorage site such as a cloud or network system 250 while virtual disk226C may be physically included within device 201. Cloud systems mayinclude an arrangement of various servers, switches, networks andstorage along with a virtualization layer (e.g., hypervisors, specialnetwork virtualizations, storage virtualizations and the like). Theseelements may then be configured to provide various services includingcloud storage, security systems, development environments, userinterfaces and the like to users. The cloud may include private and/orpublic components. For example, a cloud may be configured as a privatecloud to be used by one or more particular entities and/or via a privatenetwork while public clouds may be used by the general public over anopen network. While virtual disks 226A and 226B are illustrated as beingpart of the same cloud 250, virtual disks 226A and 226B may also beprovisioned in different clouds, servers or systems.

In some embodiments, a first virtual machine 232A can execute, on avirtual processor 228A, a control program 220 that includes a toolsstack 224. In other embodiments, one or more virtual machines 232B-C canexecuted, on a virtual processor 228B-C, a guest operating system230A-B.

Further referring to FIG. 2A, and in more detail, in one embodiment thevirtualization environment described includes a Type 2 hypervisor 202,or a hypervisor that executes within an operating system 214 executingon the computing device 201. A Type 2 hypervisor, in some embodiments,executes within an operating system 214 environment and virtual machinesexecute at a level above the hypervisor. In many embodiments, the Type 2hypervisor executes within the context of a user's operating system suchthat the Type 2 hypervisor interacts with the user's operating system.

In some embodiments, the virtualization environment includes a computingdevice 201. The computing device 201 can be any computing device, and insome embodiments the computing device 201 can be any computer, device orcomputing machine described herein. While FIG. 2A illustrates a singlecomputing device 201, in some embodiments the modules, programs, virtualmachines, and commands stored and executed by the computing device 201can be executed by more than one computing device 201. In still otherembodiments, the computing device 201 can be a server farm.

In one embodiment, the computing device 201 can include a hardware layer210 that includes one or more pieces of hardware that communicates withthe computing machine 201. In some embodiments, the hardware layer 210can include any hardware included in the computing device 201. In otherembodiments, the hardware layer 210 can include one or more physicaldisks 204, one or more physical devices 206, one or more physicalprocessors 208 and memory 216.

The hardware layer 210, in some embodiments, can include one or morephysical disks 204. A physical disk 204 can be any hard disk, while insome embodiments a physical disk 204 can be any hard disk describedherein. In some embodiments, the hardware layer 210 can include onephysical disk 204. In other embodiments, the hardware layer 210 caninclude more than one physical disk 204. The computing device 201, insome embodiments, can communicate with an external hard disk that isincluded in the hardware layer 210 as a physical disk 204.

In other embodiments, the hardware layer 210 can include a processor208. The processor 208, in some embodiments, can be any processor, whilein other embodiments the processor 208 can be any processor describedherein. The processor 208 can include one or more processing cores. Inother embodiments the computing device 201 can include one or moreprocessors 208. In some embodiments, the computing device 201 caninclude one or more different processors, e.g. a processing unit, agraphics processing unit, or a physics engine.

Physical devices 206, in some embodiments, can be any device included inthe computing device 201. In some embodiments, physical devices 206 canbe any combination of devices included in the computing device 201 andexternal devices that communicate with the computing device 201. Thecomputing device 201, in some embodiments, can include one or morephysical devices 206. A physical device 206 can be any of the following:a network interface card; a video card; a keyboard; a mouse; an inputdevice; a monitor; a display device; speakers; an optical drive; astorage device; a universal serial bus connection; any device connectedto the computing device 201; any device communicating with the computingdevice 201; a printer; a scanner; or any other device or devicedescribed herein.

The hardware layer 210 can further include physical memory 216 that caninclude any type of memory. In some embodiments, the physical memory 216can include any memory type described herein. The physical memory 216can store data, and in some embodiments can store one or more programs,or set of executable instructions. FIG. 2A illustrates one embodimentwhere firmware 212 is stored within the physical memory 216 of thecomputing device 201. Programs or executable instructions stored in thephysical memory 216 can be executed by the one or more processors 208 ofthe computing device 201.

Firmware 212, in some embodiments, can be any combination of executableinstructions and hardware that controls hardware communicating with orincluded within the computing device 201. In some embodiments, thefirmware 212 can control one or more pieces of hardware within thehardware layer 210. Firmware 212, in many embodiments, can be executedby one or more processors 208 within the computing device 201. In someembodiments, the firmware 212 can be boot firmware such as the basicinput/output system (BIOS.) Additional firmware 212 executing on thecomputing device 201 can interface with the BIOS.

In one embodiment, the computing device 201 can include an operatingsystem 214 executed by one or more physical processors 208. In someembodiments, the operating system 214 is a user operating system thatcan directly access the hardware devices in the hardware layer 210. Theoperating system 214 can be any operating system and in someembodiments, the operating system 214 can be any operating systemdescribed herein. FIG. 2A illustrates one embodiment where thehypervisor 202 executes within the context of the operating system 214executing on the computing device 201. In this embodiment, the operatingsystem 214 can be referred to as a host operating system 214, while theother operating systems can be referred to as guest operating systems.Guest operating systems can include the guest operating systems 230A-Bexecuting on the virtual machines 232, and/or the control program 220.

In some embodiments, the computing device 201 can include a hypervisor202. A hypervisor 202, in some embodiments, can be a program thatexecuted by processors 208 on the computing device 201 to manage anynumber of virtual machines. The hypervisor 202 can be referred to as avirtual machine monitor, or platform virtualization software. In someembodiments, a hypervisor 202 can be any combination of executableinstructions and hardware that monitors virtual machines executing on acomputing machine. While FIG. 2A illustrates a virtualizationenvironment that includes a Type 2 hypervisor 202, the computing device201 can execute any other type of hypervisor. For example, the computingdevice 201 can execute a virtualization environment that includes a Type1 hypervisor 202. In some embodiments, the computing device 201 canexecute one or more hypervisors 202. These one or more hypervisors 202can be the same type of hypervisor, or in other embodiments can bedifferent hypervisor types.

The hypervisor 202, in some embodiments, can provide virtual resourcesto operating systems 230 or control programs 220 executing on virtualmachines 232 in any manner that simulates the operating systems 230 orcontrol programs 220 having direct access to system resources. Systemresources can include: physical devices; physical disks; physicalprocessors; physical memory 216 and any other component included in thecomputing device 201 hardware layer 210. In these embodiments, thehypervisor 202 may be used to emulate virtual hardware, partitionphysical hardware, virtualize physical hardware, or execute virtualmachines that provide access to computing environments. In still otherembodiments, the hypervisor 202 controls processor scheduling and memorypartitioning for a virtual machine 232 executing on the computing device201. Hypervisor 202 may include those manufactured by VMWare, Inc., ofPalo Alto, Calif.; the XEN hypervisor, an open source product whosedevelopment is overseen by the open source Xen.org community; HyperV,VirtualServer or virtual PC hypervisors provided by Microsoft, orothers. In some embodiments, a computing device 201 executes ahypervisor 202 that creates a virtual machine platform on which guestoperating systems may execute. In these embodiments, the computingdevice 201 can be referred to as a host server. An example of such acomputing device is the XEN SERVER provided by Citrix Systems, Inc., ofFort Lauderdale, Fla.

In one embodiment, the hypervisor 202 can create a virtual machine232A-B (generally 232) in which an operating system 230 executes. In oneof these embodiments, for example, the hypervisor 202 loads a virtualmachine image to create a virtual machine 232. In another of theseembodiments, the hypervisor 202 executes an operating system 230 withinthe virtual machine 232. In still another of these embodiments, thevirtual machine 232 executes an operating system 230.

In one embodiment, the hypervisor 202 controls the execution of at leastone virtual machine 232. In another embodiment, the hypervisor 202presents at least one virtual machine 232 with an abstraction of atleast one hardware resource provided by the computing device 201. Theabstraction can further be referred to as a virtualization or virtualview of the hardware, memory processor and other system resourcesavailable on the computing device 201. Hardware or hardware resources,in some embodiments, can be any hardware resource available within thehardware layer 210. In other embodiments, the hypervisor 202 controlsthe manner in which virtual machines 232 access the physical processors208 available in the computing device 201. Controlling access to thephysical processors 208 can include determining whether a virtualmachine 232 should have access to a processor 208, and how physicalprocessor capabilities are presented to the virtual machine 232.

In some embodiments, the computing device 201 can host or execute one ormore virtual machines 232. A virtual machine 232 can be called a domain,a guest and/or a DOMAIN U. A virtual machine 232 is a set of executableinstructions that, when executed by a processor 208, imitate theoperation of a physical computer such that the virtual machine 232 canexecute programs and processes much like a physical computing device.While FIG. 2A illustrates an embodiment where a computing device 201hosts three virtual machines 232, in other embodiments the computingdevice 201 can host any number of virtual machines 232. The hypervisor202, in some embodiments, provides each virtual machine 232 with aunique virtual view of the physical hardware, memory, processor andother system resources available to that virtual machine 232. In someembodiments, the unique virtual view can be based on any of thefollowing: virtual machine permissions; application of a policy engineto one or more virtual machine identifiers; the user accessing a virtualmachine; the applications executing on a virtual machine; networksaccessed by a virtual machine; or any other similar criteria. Thehypervisor 202, in other embodiments, provides each virtual machine 232with a substantially similar virtual view of the physical hardware,memory, processor and other system resources available to the virtualmachines 232.

Each virtual machine 232 can include a virtual disk 226A-C (generally226) and a virtual processor 228A-C (generally 228.) The virtual disk226, in some embodiments, is a virtualized view of one or more physicaldisks 204 of the computing device 201, or a portion of one or morephysical disks 204 of the computing device 201. The virtualized view ofthe physical disks 204 can be generated, provided and managed by thehypervisor 202. In some embodiments, the hypervisor 202 provides eachvirtual machine 232 with a unique view of the physical disks 204. Thus,in these embodiments, the virtual disk 226 provisioned for each virtualmachine 232 can be unique when compared with the other virtual disks226.

A virtual processor 228 can be a virtualized view of one or morephysical processors 208 of the computing device 201. In someembodiments, the virtualized view of the physical processors 208 can begenerated, provided and managed by the hypervisor 202. In someembodiments, the virtual processor 228 has substantially all of the samecharacteristics of at least one physical processor 208. In otherembodiments, the virtual processor 208 provides a modified view of thephysical processors 208 such that at least some of the characteristicsof the virtual processor 228 are different than the characteristics ofthe corresponding physical processor 208.

A control program 220 may execute at least one application for managingand configuring the guest operating systems executing on the virtualmachines 232 and in some embodiments the computing device 201. In someembodiments, the control program 220 can be called a control operatingsystem, a control domain, domain 0 or dom 0. The control program 220, insome embodiments, can be DOMAIN o or DOM0 of the XEN hypervisor. Thecontrol program 220 can execute an administrative application or programthat can further display a user interface which administrators can useto access the functionality of each virtual machine 232 and/or to managethe virtual machines 232. In some embodiments, the user interfacegenerated by the administrative program can be used to terminate theexecution of virtual machines 232, allocate resources to virtualmachines 232, assign permissions to virtual machines 232, or managesecurity credentials associated with virtual machines 232. The controlprogram 220, in some embodiments, can start new virtual machines 232 orterminate execution of executing virtual machines 232. In otherembodiments, the control program 220 can directly access hardware and/orresources within the hardware layer 210. In still another embodiment,the control program 220 can interface with programs and applicationsexecuting on the computing device 210 and outside of the context of avirtual machine 232. Similarly, the control program 220 can interfacewith programs and applications executing within the context of a virtualmachine 232.

In one embodiment, the hypervisor 202 can execute the control program220 within a virtual machine 232. The hypervisor 202 can create andstart the virtual machine 232. In embodiments where the hypervisor 202executes the control program 220 within a virtual machine 232, thatvirtual machine 232 can be referred to as the control virtual machine232. In still another embodiment, the control program 220 executeswithin a virtual machine 232 that is authorized to directly accessphysical resources on the computing device 201.

In some embodiments, a control program 220A (Not Shown) on a firstcomputing device 201A (Not Shown) may exchange data with a controlprogram 220B (Not Shown) on a second computing device 201B (Not Shown).In these embodiments the first computing device 201A may be locatedremote from the second computing device 201B. The control programs220A-B can exchange data via a communication link between a hypervisor202A (Not Shown) executing on the first computing device 201A and ahypervisor 202B (Not Shown) executing on the second computing device201B. Through this communication link, the computing devices 201A-B canexchange data regarding processors and other physical resourcesavailable in a pool of resources. Further, through this connectionbetween hypervisors 202A-B, the hypervisors 202A-B can manage a pool ofresources, e.g. the resources available on the first computing device201A and the second computing device 201B, distributed across one ormore computing devices 201A-B. The hypervisors 202A-B can furthervirtualize these resources and make them available to virtual machines232 executing on the computing devices 201A-B. In another instance ofthis embodiment, a single hypervisor 202 can manage and control virtualmachines 232 executing on both computing devices 201A-B.

In some embodiments, the control program 220 interacts with one or moreguest operating systems 230A-B (generally 230.) The control program 220can communicate with the guest operating systems 230 through ahypervisor 202. Through the hypervisor 202, the guest operating system230 can request access to physical disks 204, physical processors 208,memory 216, physical devices 206 and any other component in the hardwarelayer 210. In still other embodiments, the guest operating systems 230can communicate with the control program 220 via a communication channelestablished by the hypervisor 202, such as, for example, via a pluralityof shared memory pages made available by the hypervisor 202.

In some embodiments, the control program 220 includes a network back-enddriver for communicating directly with networking hardware provided bythe computing device 201. In one of these embodiments, the networkback-end driver processes at least one virtual machine request from atleast one guest operating system 230. In other embodiments, the controlprogram 220 includes a block back-end driver for communicating with astorage element on the computing device 201. In one of theseembodiments, the block back-end driver reads and writes data from thestorage element based upon at least one request received from a guestoperating system 230.

In another embodiment, the control program 220 includes a tools stack224. In another embodiment, a tools stack 224 provides functionality forinteracting with the hypervisor 202, communicating with other controlprograms 220 (for example, on a second computing device 201B), ormanaging virtual machines 232 on the computing device 201. In anotherembodiment, the tools stack 224 includes customized applications forproviding improved management functionality to an administrator of avirtual machine farm. In some embodiments, at least one of the toolsstack 224 and the control program 220 include a management API thatprovides an interface for remotely configuring and controlling virtualmachines 232 running on a computing device 201. In other embodiments,the control program 220 communicates with the hypervisor 202 through thetools stack 224.

In one embodiment, the hypervisor 202 executes a guest operating system230 within a virtual machine 232 created by the hypervisor 202. Inanother embodiment, the guest operating system 230 provides a user ofthe computing device 201 with access to resources within a computingenvironment. In still another embodiment, a resource includes a program,an application, a document, a file, a plurality of applications, aplurality of files, an executable program file, a desktop environment, acomputing environment, or other resource made available to a user of thecomputing device 201. In yet another embodiment, the resource may bedelivered to the computing device 201 via a plurality of access methodsincluding, but not limited to, conventional installation directly on thecomputing device 201, delivery to the computing device 201 via a methodfor application streaming, delivery to the computing device 201 ofoutput data generated by an execution of the resource on a secondcomputing device 201′ and communicated to the computing device 201 via apresentation layer protocol, delivery to the computing device 201 ofoutput data generated by an execution of the resource via a virtualmachine executing on a second computing device 201′, or execution from aremovable storage device connected to the computing device 201, such asa USB device, or via a virtual machine executing on the computing device201 and generating output data. In some embodiments, the computingdevice 201 transmits output data generated by the execution of theresource to another computing device 201′.

In one embodiment, the guest operating system 230, in conjunction withthe virtual machine on which it executes, forms a fully-virtualizedvirtual machine that is not aware that it is a virtual machine; such amachine may be referred to as a “Domain U HVM (Hardware Virtual Machine)virtual machine”. In another embodiment, a fully-virtualized machineincludes software emulating a Basic Input/Output System (BIOS) in orderto execute an operating system within the fully-virtualized machine. Instill another embodiment, a fully-virtualized machine may include adriver that provides functionality by communicating with the hypervisor202. In such an embodiment, the driver is typically aware that itexecutes within a virtualized environment.

In another embodiment, the guest operating system 230, in conjunctionwith the virtual machine on which it executes, forms a paravirtualizedvirtual machine, which is aware that it is a virtual machine; such amachine may be referred to as a “Domain U PV virtual machine”. Inanother embodiment, a paravirtualized machine includes additionaldrivers that a fully-virtualized machine does not include. In stillanother embodiment, the paravirtualized machine includes the networkback-end driver and the block back-end driver included in a controlprogram 220, as described above.

Illustrated in FIG. 2B is another embodiment of a virtualizationenvironment that illustrates a Type 1 hypervisor 202. Executing on thecomputing device 201 is a hypervisor 202 that can directly access thehardware and resources within the hardware layer 210. Virtual machines232 managed by the hypervisor 202 can be an unsecure virtual machine232B and/or a secure virtual machine 232C. Whereas the virtualizationenvironment depicted in FIG. 2A illustrates a host operating system 214,the virtualization environment embodiment in FIG. 2B does not execute ahost operating system.

Further referring to FIG. 2B, and in more detail, the virtualizationenvironment includes a Type 1 hypervisor 202. Type 1 hypervisors 202, insome embodiments, execute on “bare metal,” such that the hypervisor 202has direct access to all applications and processes executing on thecomputing device 201, all resources on the computing device 201 and allhardware on the computing device 201 or communicating with the computingdevice 201. While a Type 2 hypervisor 202 accesses system resourcesthrough a host operating system 214, a Type 1 hypervisor 202 candirectly access all system resources. The Type 1 hypervisor 202 canexecute directly on one or more physical processors of the computingdevice 201, and can include program data stored in the physical memory216.

In a virtualization environment that employs a Type 1 hypervisor 202configuration, the host operating system can be executed by one or morevirtual machines 232. Thus, a user of the computing device 201 candesignate one or more virtual machines 232 as the user's personalmachine. This virtual machine can imitate the host operating system byallowing a user to interact with the computing device 201 insubstantially the same manner that the user would interact with thecomputing device 201 via a host operating system 214.

Virtual machines 232 can be unsecure virtual machines 232B and securevirtual machine 232C. While FIG. 2B illustrates a secure and unsecurevirtual machine, sometimes they can be referred to as privileged andunprivileged virtual machines. In some embodiments, a virtual machine'ssecurity can be determined based on a comparison of the virtual machineto other virtual machines executing within the same virtualizationenvironment. For example, were a first virtual machine to have access toa pool of resources, and a second virtual machine not to have access tothe same pool of resources; the second virtual machine could beconsidered an unsecure virtual machine 232B while the first virtualmachine could be considered a secure virtual machine 232A. In someembodiments, a virtual machine's 323 ability to access one or moresystem resources can be configured using a configuration interfacegenerated by either the control program 220 or the hypervisor 202. Inother embodiments, the level of access afforded to a virtual machine 232can be the result of a review of any of the following sets of criteria:the user accessing the virtual machine; one or more applicationsexecuting on the virtual machine; the virtual machine identifier; a risklevel assigned to the virtual machine based on one or more factors; orany other similar criteria.

In some embodiments, unsecure virtual machines 232B may be preventedfrom accessing resources, hardware, memory locations, and programs thatsecure virtual machines 232A may access. For example, a secure virtualmachine 232C may be able to access one or more company resources, whilethe unsecure virtual machine 232B cannot access any company resources.

Illustrated in FIG. 3 is one embodiment of a system that includes acomputing device 201 executing a virtualization environment 302 and acomputing device 203 that executes a virtual desktop infrastructure(VDI) platform 310 and a performance monitoring system 316. Thevirtualization environment 302 executing on the computing device 201,can be any virtualization environment described herein. The illustratedembodiment depicts a virtualization environment 302 that includes ahypervisor 202, a control virtual machine 232A and one or moreadditional virtual machines 232B. The control virtual machine 232A caninclude a control program 220 communicating with a virtual disk 226Aassociated with metadata 322. The control program 220 can furtherinclude a disk type database 350 which can store the metadata 322associated with the virtual disks 226 of the virtualization environment302. The additional virtual machine(s) 232B can execute a guestoperating system 230A that communicates with a virtual disk 226Bassociated with metadata 322. The computing device 201 can include ahardware layer 201 that interfaces with the hypervisor 202 and thatincludes a storage subsystem 316. The other computing device 203 caninclude a VDI platform 310 that can encompass a virtual machine templatepool 318 of one or more virtual machine templates 323A-N (hereingenerally referred to as virtual machine template 323) and a group ofVDI user sessions 314 that includes one or more user sessions 304A-N(herein generally referred to a user sessions 304.) The other computingdevice 203 can also execute a virtual machine creator 330.

Further referring to FIG. 3, and in more detail, in one embodiment eachcomputing device 201, 203 can be any computing device 100 describedherein. In some embodiments, the computing devices 201, 203 can be aserver 106 or a client 102. The computing devices 201, 203 can bereferred to a first computer, a second computer, a third computer, etc.Furthermore, the computing devices 201, 203 can communicate with oneanother over a network such as any network 104 described herein. In oneembodiment one computing device 201 can be a remote computer 201, whilethe other computing device can be a local computer 203. As the computingdevices 201, 203 can be any computing machine 100 described herein, sotoo the hardware layer 210 can be any hardware layer 210 describedherein and can include any computer hardware described herein.

The virtualization environment 302 executing on the computing device201, can be any virtualization environment described herein. Inparticular, the virtualization environment 302 can include anyhypervisor configuration, or either the hypervisor configurationillustrated in FIG. 2A or the hypervisor configuration illustrated inFIG. 2B. In one embodiment, the hypervisor 202 included in thevirtualization environment 302 can be any hypervisor 202, or anyhypervisor 202 described herein.

Having described in FIGS. 1-3 various examples computing devices,computing environments, and certain software and functionality that maybe included in such systems, it will be appreciated that other softwareand hardware may be used other than those which are identified above. Inaddition, the following paragraphs provide additional examples ofvarious methods and systems relating to the migration of a virtualmachine while preserving security of a storage repository provisioned tothe virtual machine.

FIG. 4 is a flowchart illustrating an example method by which a virtualmachine may be migrated between two devices, virtualizationenvironments, or domains while preserving the security of an associatedstorage repository. In one example, the preservation of security mayinclude preventing a previous device, host or domain (e.g., a transferorvirtualization environment) from being able to access the encryptedstorage once the associated virtual machine has been migrated to the newdevice. In step 400, a first device on which a virtual machine currentlyexists may provision a storage repository for the virtual machine. Forexample, provisioning a storage repository may include partitioningstorage space on a server for a particular virtual machine and/orallocating storage space on a cloud. In some examples, one or multiplecomponents within a cloud integration layer of a public or private cloudcan provision a storage repository for the virtual machine, such as acontrol virtual machine instructing a hypervisor to provision storageand allocating that storage to the virtual machine. A cloudinfrastructure platform, in some instances, can provision storage to avirtualization environment or domain prior to provisioning a storagerepository to a particular virtual machine. In step 405, the firstdevice may generate and encrypt the storage repository using a storageencryption key K1. The storage encryption key K1 may be generated basedon any of various known encryption protocols such as AES, Triple DigitalEncryption Standard (DES), and the like. The storage encryption key K1may then be stored in a header section of the storage repository in step410. In some examples, the header section of the storage repository maybe logically separate from a remainder of the storage repository andthus, might not be encrypted by storage encryption key K1. Thus, theheader may be separately accessed and/or encrypted from a data storagesection of the repository.

In step 415, the first device may further generate a second key H1VM1with which the storage encryption key K1 is subsequently encrypted. Thesecond key H1VM1 may then be stored in a key storage area, as describedin additional detail below. By encrypting the storage encryption key K1,access to the storage repository may be secured by controlling access tothe storage encryption key K1. Accordingly, in order to access storageencryption key K1 to decrypt the data stored in the data repository, asystem or user must have knowledge of second key H1VM1 (e.g., to decryptthe storage encryption key K1). The storage repository may then bedecrypted using the decrypted storage encryption key. Using such asecurity mechanism, access controls for the storage repository may bemodified without having to decrypt the entire storage repository with anold storage encryption key K1 and to subsequently re-encrypt the entirestorage repository with a new storage encryption key. Instead, only theencryption key H1VM1 might be replaced to affect the access controlmodification without having to modify the underlying storage encryptionkey (e.g., key K1).

FIG. 5 illustrates an example block diagram of a storage repositorystructure. Storage repository 501 may include a storage header 505 and adata storage section 507. Data may be stored in section 507 whileparameters, flags, metadata and the like may be stored in header section505. Header section 505 may further include a storage encryption key 509used to encrypt data storage section 507. As described, storageencryption key 509 maybe encrypted using one or more keys specified in akey storage area 511. Key storage area 511 may be included within headersection 505. In one or more other examples, key storage 511 may bestored separately from the data storage repository 501. Key storage area511 may include slots 0-3 that may be configured to store encryptionkeys used to encrypt the storage encryption key 509 thereby controllingoverall access to storage repository 501. For example, modifying keyslots of key storage 511 (e.g., storing keys thereto and removing keystherefrom) may be controlled using the encryption keys. While 4 keyslots are illustrated in FIG. 5, the key storage area 511 may storefewer or more key slots as needed or necessary. Changes to header 505and access to the storage repository 501 may be facilitated usingapplication protocol interfaces (APIs). For example, new keys may beinserted into a slot of the key storage area 511 using an API using thenew key as a parameter or input. Similarly, a key may be deleted fromkey storage area 511 using a deletion API specifying a slot from whichthe key is to be deleted. In another example, retrieving data from thestorage section 507 by using a data retrieval API that requires a keycorresponding to one or more of the keys stored in key storage 511 as aparameter.

Referring again to FIG. 4, the first device may receive a request tomigrate the virtual machine associated with the storage repository toanother device (e.g., a second device) in step 420. In response thereto,the first device may generate and use a transfer key TK1 to encrypt thestorage encryption key K1 in step 425. Transfer key TK1 thus effectivelyreplaces a previous encryption key, such as key H1VM1, as the key withwhich the storage encryption key is encrypted. For example, the firstdevice may initially decrypt the storage encryption key using H1VM1 thenre-encrypt the storage encryption key using TK1 without having todecrypt and re-encrypt an entire data storage area of the datarepository. In some examples, the storage encryption key may beencrypted with the transfer key TK1 by creating a new instantiation ofthe storage encryption key and encrypting the new instantiation. Theprevious instantiation (encrypted using a previously encryption key) maythen be deleted. The transfer key TK1 may then be stored in the keystorage area in one of the slots and key H1VM1 may be deleted orotherwise removed from the key storage area. A transfer key TK1 may beused instead of H1VM1 for the migration of the virtual machine in theevent H1VM1 is to be used again or is used for other encryption by thefirst device. Accordingly, the first device may wish to maintain thesecrecy of H1VM1 and therefore, might not transfer H1VM1 to themigration destination device or even off of the first device. In step430, the first device may initiate the migration of the virtual machineto the destination second device. Migration of the virtual machine mayinclude saving a current state of the virtual machine and copying thestate information from one device to the other and a recipient deviceinstantiating a new virtual machine using the received stateinformation.

The first device may further transmit transfer key TK1 through a securecommunication channel to the second device in step 435 along with theheader section of the storage repository. In some examples, the headerand the transfer key may be transmitted in the same channel or indifferent channels. The secure channel through which the transfer keyand/or the header is transmitted may be different from a channel throughwhich one or more other communications or types of communicationsassociated with the virtual machine migration is transmitted. Once thevirtual machine has been migrated and the transfer key TK1 and thestorage repository header received, the destination second device may,in step 440, generate a new key H2VM1 to replace the transfer key TK1.Additionally, in step 445, the second device may import the receivedheader into the storage repository. The second device may then encryptthe storage encryption key K1 using H2VM1 within the imported header instep 450 using transfer key TK1. For example, the device may invoke astorage key encryption API using the transfer key TK1 and new key H2VM1as inputs or parameters. The passing of TK1 in the storage keyencryption API may evidence authorization to re-encrypt (or encrypt anew instantiation of) storage encryption key K1 using the new key.Additionally, the second device may remove key TK1 from the key storagearea once the storage encryption key has been encrypted with the new keyH2VM1 and store new key H2VM1 to the key storage area of the storagerepository header. Using the foregoing process, the storage repositorymay be re-secured using a new key that is not known to the previousdevice, i.e., the first device, without requiring a complete decryptionand re-encryption of the file system/storage repository.

FIGS. 6A-6D illustrate a virtual machine migration process withcorresponding structures and changes thereto. FIG. 6A illustrates, forexample, computing device 601 providing virtual machine 603. Storagerepository 603 may be provisioned for virtual machine 602 and may existwithin a cloud system as discussed herein. In some instances, thestorage repository 603 may be managed or otherwise regulated via a cloudinfrastructure platform such as CLOUDSTACK or OPENSTACK. In otherarrangements, a storage repository may be physically located within thesame device (e.g., device 601). The device 601 may further encryptstorage repository 603 using a storage encryption key 609 stored to aheader section 605 of the storage repository 603. Additionally, thedevice 601 may generate an encryption key H1VM1 for encrypting thestorage encryption key 609 and store it to a slot, such as slot 0, ofkey storage area 611.

In FIG. 6B, upon receiving a request to migrate the virtual machine 602to a new device, device 601 may generate a transfer key TK1 and storethat transfer key into slot 1 of key storage area 611. The host 601 mayfurther re-encrypt the storage encryption key 609 with TK1 andsubsequently remove encryption key H1VM1 from slot 0. After the processof FIG. 6B, storage encryption key 609 will be encrypted with TK1 ratherthan H1VM1.

FIG. 6C illustrates the migration of virtual machine 602 from device 601to device 621. As part of the migration, the transfer key TK1 may betransmitted to device 621 in a secure manner with or separately from aheader section 605 of the storage repository 603. Once the virtualmachine 602 has been migrated to device 621, device 621 may generate itsown secret key H1VM2 for re-encrypting the storage encryption key 609and may further store key H1VM2 to key storage area 611 (e.g., in slot2). Similar to the process of replacing H1VM1 in FIG. 6B, device 621 maydecrypt storage encryption key 609 with TK1 and re-encrypt the storageencryption key 609 with H1VM2. TK1 may then be deleted from key storagearea 611.

FIG. 6D illustrates a migrated virtual machine 602 and virtual machine602 with the storage encryption key 609 newly encrypted with device621's own key H1VM2, as shown in key storage area 611. Accordingly,without knowledge of H1VM2, the previous device, i.e., host 601, islikely unable to be able to access storage repository 603.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined herein is not necessarily limited to thespecific features or acts described above. Rather, the specific featuresand acts described above are disclosed as illustrative forms.

What is claimed is:
 1. A non-transitory computer-readable medium storinginstructions that, when executed by a processor of an apparatus, causethe apparatus to: encrypt a storage area provisioned for a virtual oractual machine with a first encryption key, the storage area storingdata; store the first encryption key in a header of the storage area,wherein the header and the data stored in the storage area are logicallyseparate from one another; generate a second encryption key and storethe second encryption key in the header; encrypt the header and thefirst encryption key stored therein with a second encryption key; andmigrate the storage area, including: decrypting the first encryption keywith the second encryption key; encrypting the first encryption key witha third encryption key; and removing the second encryption key from theheader after encrypting the first encryption key with the thirdencryption key.
 2. The non-transitory computer-readable medium of claim1, wherein the instructions, when executed, further cause the apparatusto encrypt, using the third encryption key, the header comprising thefirst encryption key.
 3. The non-transitory computer-readable medium ofclaim 1, wherein migrating the storage area is performed withoutmodifying encryption of the data.
 4. The non-transitorycomputer-readable medium of claim 1, wherein the instructions, whenexecuted, cause the apparatus to migrate, from a first device of avirtualization environment to a second device of the virtualizationenvironment, the data.
 5. The non-transitory computer-readable medium ofclaim 4, wherein the instructions, when executed, further cause theapparatus to: migrate, from the first device and to the second device,state information associated with the virtual machine; instantiate, onthe second device and based on the state information, a new virtualmachine; and provide the new virtual machine with access to the data. 6.A method comprising: encrypting a storage area provisioned for a virtualor actual machine with a first encryption key, the storage area storingdata; storing the first encryption key in a header of the storage area,wherein the header and the data stored in the storage area are logicallyseparate from one another; generating a second encryption key and storethe second encryption key in the header; encrypting the header and thefirst encryption key stored therein with a second encryption key; andmigrating the storage area, including: decrypting the first encryptionkey with the second encryption key; encrypting the first encryption keywith a third encryption key; and removing the second encryption key fromthe header after encrypting the first encryption key with the thirdencryption key.
 7. The method of claim 6, further comprising encrypting,using the third encryption key, the header comprising the firstencryption key.
 8. The method of claim 6, wherein migrating the storagearea is performed without modifying encryption of the data.
 9. Themethod of claim 6, wherein migrating the storage area further includesmigrating, from a first device of a virtualization environment to asecond device of the virtualization environment, the data.
 10. Themethod of claim 9, wherein migrating the storage area further includes:migrating, from the first device and to the second device, stateinformation associated with the virtual machine; instantiating, on thesecond device and based on the state information, a new virtual machine;and providing the new virtual machine with access to the data.
 11. Anapparatus comprising: a processor; and memory storing computer readableinstructions that, when executed by the processor, cause the apparatusto: encrypt a storage area provisioned for a virtual or actual machinewith a first encryption key, the storage area storing data; store thefirst encryption key in a header of the storage area, wherein the headerand the data stored in the storage area are logically separate from oneanother; generate a second encryption key and store the secondencryption key in the header; encrypt the header and the firstencryption key stored therein with a second encryption key; and migratethe storage area, including: decrypting the first encryption key withthe second encryption key; encrypting the first encryption key with athird encryption key; and removing the second encryption key from theheader after encrypting the first encryption key with the thirdencryption key.
 12. The apparatus of claim 11, wherein the instructions,when executed, further cause the apparatus to encrypt, using the thirdencryption key, the header comprising the first encryption key.
 13. Theapparatus of claim 11, wherein migrating the storage area is performedwithout modifying encryption of the data.
 14. The apparatus of claim 11,wherein the instructions, when executed, cause the apparatus to migrate,from a first device of a virtualization environment to a second deviceof the virtualization environment, the data.
 15. The apparatus of claim14, wherein the instructions, when executed, further cause the apparatusto: migrate, from the first device and to the second device, stateinformation associated with the virtual machine; instantiate, on thesecond device and based on the state information, a new virtual machine;and provide the new virtual machine with access to the data.